|
Many email clients now offer some support for Unicode. While some use Unicode by default,〔https://support.google.com/mail/answer/22841?hl=en〕 many others will automatically choose between a legacy encoding and Unicode depending on the mail's content, either automatically〔https://github.com/wanderlust/apel/blob/apel-wl/mcs-20.el#L189〕 or when the user requests it.〔http://smallbusiness.chron.com/setting-outlook-use-utf8-32242.html〕 Technical requirements for sending of messages containing non-ASCII characters by email include * encoding of certain header fields (subject, sender’s and recipient’s names, sender’s organization and reply-to name) and, optionally, body in a content-transfer encoding * encoding of non-ASCII characters in one of the Unicode transforms * negotiating the use of UTF-8 encoding in email addresses and reply codes (SMTPUTF8) * sending the information about the content-transfer encoding and the Unicode transform used so that the message can be correctly displayed by the recipient (see Mojibake). If the sender’s or recipient’s email address contains non-ASCII characters, sending of a message requires also encoding of these to a format that can be understood by mail servers. == Unicode support in protocols == * RFC 6531 provides a mechanism for allowing non-ASCII email addresses encoded as UTF-8 in an SMTP〔(SMTP Extension for Internationalized Email )〕 or LMTP protocol 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Unicode and email」の詳細全文を読む スポンサード リンク
|